home *** CD-ROM | disk | FTP | other *** search
-
-
-
- - 1 -
-
-
-
- 2. _I_n_s_t_a_l_l_a_t_i_o_n__I_n_f_o_r_m_a_t_i_o_n
-
- This chapter lists supplemental information to the _I_R_I_S
- _S_o_f_t_w_a_r_e _I_n_s_t_a_l_l_a_t_i_o_n _G_u_i_d_e. The information listed here is
- product- and release-specific; use it with the Installation
- Guide to install this product.
-
- 2.1 _I_R_I_X__I_n_t_e_r_a_c_t_i_v_e__D_e_s_k_t_o_p__S_u_b_s_y_s_t_e_m_s
-
- The IRIX Interactive Desktop includes these subsystems:
-
- _d_e_s_k_t_o_p__e_o_e._b_o_o_k_s._C_o_n_f_T_e_s_t_E_r_r_o_r_s Help on understanding
- errors that may be detected
- while running the confidence
- tests.
-
- _d_e_s_k_t_o_p__e_o_e._b_o_o_k_s._C_o_n_f_T_e_s_t_H_e_l_p Help on the confidence tests
- for checking system hardware.
-
- _d_e_s_k_t_o_p__e_o_e._b_o_o_k_s._D_e_s_k_t_o_p__U_G The Desktop User's Guide.
- InSight documentation on the
- IRIX Interactive Desktop.
-
- _d_e_s_k_t_o_p__e_o_e._b_o_o_k_s._E_r_r_o_r_M_e_s_s_a_g_e_H_e_l_p Help for error messages
- that may occur when using the
- IRIX Interacive Desktop.
-
- _d_e_s_k_t_o_p__e_o_e._b_o_o_k_s._H_o_w_D_o_I__H_e_l_p Context-sensitive help
- information for each of the
- IRIX Interactive Desktop
- tools.
-
- _d_e_s_k_t_o_p__e_o_e._b_o_o_k_s._P_e_r_S_y_s_A_d_m_i_n InSight documentation on
- administering your IRIX
- Interactive Desktop system.
-
- _d_e_s_k_t_o_p__e_o_e._b_o_o_k_s._W_e_b_J_u_m_p_e_r_H_e_l_p Help for using WebJumper to
- create webjumper or jumpsite
- icons.
-
- _d_e_s_k_t_o_p__e_o_e._d_a_t_a._j_u_m_p_s_i_t_e_s Jumpsites for SiliconSurf,
- SupportInfo, and
- SupportLibrary.
-
- _d_e_s_k_t_o_p__e_o_e._m_a_n._e_o_e Manual pages for all IRIX Interactive
- Desktop Tools.
-
- _d_e_s_k_t_o_p__e_o_e._m_a_n._r_e_l_n_o_t_e_s These release notes.
-
- _d_e_s_k_t_o_p__e_o_e._s_w._C_o_n_f_i_d_e_n_c_e Confidence tests used for testing
- system hardware.
-
-
-
-
-
-
-
-
-
-
-
- - 2 -
-
-
-
- _d_e_s_k_t_o_p__e_o_e._s_w._D_e_s_k_s Software for creating and managing
- multiple desktops on your
- display.
-
- _d_e_s_k_t_o_p__e_o_e._s_w._c_o_n_t_r_o_l__p_a_n_e_l_s Customization panels to allow
- users to change various
- interface attributes such as
- the background or the mouse
- speed.
-
- _d_e_s_k_t_o_p__e_o_e._s_w._e_n_v_m The main iconic interface, including the
- file manager, the icon
- catalog, the search tool, and
- WebJumper.
-
- _d_e_s_k_t_o_p__e_o_e._s_w._s_h_a_r_e Shared data files, including the legal
- notice and session warning
- messages.
-
- _d_e_s_k_t_o_p__e_o_e._s_w._t_o_o_l_c_h_e_s_t The toolchest application, a front
- end to accessing many common
- tools, including most of the
- IRIX Interactive Desktop.
-
-
- 2.2 _I_R_I_X _I_n_t_e_r_a_c_t_i_v_e _D_e_s_k_t_o_p _S_u_b_s_y_s_t_e_m _D_i_s_k _S_p_a_c_e
- _R_e_q_u_i_r_e_m_e_n_t_s
-
- This section lists the subsystems of the IRIX Interactive
- Desktop and their sizes.
-
- If you are installing this product for the first time, the
- subsystems marked ``default'' are the ones that are
- installed if you use the ``go'' menu item. To install a
- different set of subsystems, use the ``install,''
- ``remove,'' ``keep,'' and ``step'' commands in _i_n_s_t to
- customize the list of subsystems to be installed, then
- select the ``go'' menu item. While running _i_n_s_t, you can
- also use the command
-
- aaaaddddmmmmiiiinnnn ffffiiiilllleeeessss _s_u_b_s_y_s_t_e_m
-
- to view the files contained in _s_u_b_s_y_s_t_e_m.
-
- You can also use the graphical inst tool, _s_w_m_g_r, which is
- accessible from the System toolchest as the Software Manager
- menu item, to install the software when you are not in the
- miniroot.
-
- Note: The listed subsystem sizes are approximate. Refer to
- the _I_R_I_S _S_o_f_t_w_a_r_e _I_n_s_t_a_l_l_a_t_i_o_n _G_u_i_d_e for information
-
-
-
-
-
-
-
-
-
-
-
- - 3 -
-
-
-
- on finding exact sizes.
-
- Subsystem Name Subsystem Size
- (Kbyte)
- _d_e_s_k_t_o_p__e_o_e._b_o_o_k_s._C_o_n_f_T_e_s_t_E_r_r_o_r_s (default) 360
- _d_e_s_k_t_o_p__e_o_e._b_o_o_k_s._C_o_n_f_T_e_s_t_H_e_l_p (default) 388
- _d_e_s_k_t_o_p__e_o_e._b_o_o_k_s._D_e_s_k_t_o_p__U_G (default) 1396
- _d_e_s_k_t_o_p__e_o_e._b_o_o_k_s._E_r_r_o_r_M_e_s_s_a_g_e_H_e_l_p (default) 348
- _d_e_s_k_t_o_p__e_o_e._b_o_o_k_s._H_o_w_D_o_I__H_e_l_p (default) 396
- _d_e_s_k_t_o_p__e_o_e._b_o_o_k_s._P_e_r_S_y_s_A_d_m_i_n (default) 988
- _d_e_s_k_t_o_p__e_o_e._b_o_o_k_s._W_e_b_J_u_m_p_e_r_H_e_l_p (default) 340
- _d_e_s_k_t_o_p__e_o_e._d_a_t_a._j_u_m_p_s_i_t_e_s (default) 12
- _d_e_s_k_t_o_p__e_o_e._m_a_n._e_o_e (default) 248
- _d_e_s_k_t_o_p__e_o_e._m_a_n._r_e_l_n_o_t_e_s (default) 56
- _d_e_s_k_t_o_p__e_o_e._s_w._C_o_n_f_i_d_e_n_c_e (default) 1164
- _d_e_s_k_t_o_p__e_o_e._s_w._D_e_s_k_s (default) 200
- _d_e_s_k_t_o_p__e_o_e._s_w._c_o_n_t_r_o_l__p_a_n_e_l_s (default) 1816
- _d_e_s_k_t_o_p__e_o_e._s_w._e_n_v_m (default) 1608
- _d_e_s_k_t_o_p__e_o_e._s_w._s_h_a_r_e (default) 24
- _d_e_s_k_t_o_p__e_o_e._s_w._t_o_o_l_c_h_e_s_t (default) 616
-
-
-
- 2.3 _I_n_s_t_a_l_l_a_t_i_o_n__M_e_t_h_o_d
-
- All of the subsystems for desktop_eoe can be installed using
- IRIX. You do not need to use the miniroot. Refer to the
- _I_R_I_S _S_o_f_t_w_a_r_e _I_n_s_t_a_l_l_a_t_i_o_n _G_u_i_d_e for complete installation
- instructions.
-
- 2.4 _P_r_e_r_e_q_u_i_s_i_t_e_s
-
- The desktop subsystem has no prerequisite on the
- sysadmdesktop subsystem. If you want to use removable media
- with the IRIX Interactive Desktop, you should install the
- sysadmdesktop subsystem.
-
- If you want to install any of the desktop_eoe.books
- subsystems, you must also install insight.sw.client.
-
- If you want to install desktop_eoe.sw.toolchest, you must
- also install desktop_base.sw.dso and motif_eoe.sw.eoe.
-
-
-
-
-
-
-
-
-
-
-
-
- - 4 -
-
-
-
- If you want to install desktop_eoe.sw.control_panels, you
- must also install desktop_base.sw.dso, motif_eoe.sw.eoe, and
- ViewKit_eoe.sw.base.
-
- If you want to install desktop_eoe.sw.Desks, you must also
- install desktop_base.sw.dso, motif_eoe.sw.eoe,
- ViewKit_eoe.sw.base, and 4Dwm.sw.4Dwm.
-
- If you want to install desktop_eoe.sw.envm, you must also
- install desktop_base.sw.dso,
- desktop_base.sw.FileTypingRules, motif_eoe.sw.eoe,
- ViewKit_eoe.sw.base, 4Dwm.sw.4Dwm, and il_eoe.sw.c++.
-
- All of the above prerequisites will be enforced
- automatically by the installation tool.
-
- If you wish to hear audio feedback for various desktop
- operations, you should install dmedia_eoe.sw.soundscheme.
-
- If you want to use the desktop to examine the contents of
- CDROMs, you should install eoe.sw.cdrom.
-
- If you want complete functionality in the dirview Media
- Previewer, you must install all media_warehouse subsystems.
- That is, if you want dirviews to be able to show contents of
- files, install the following media_warehouse.sw subsystems:
- viewers, viewers_audio, viewers_html, viewers_image,
- viewers_inventor, and viewers_movie.
-
-
-
- 2.5 _C_o_m_p_a_t_i_b_i_l_i_t_y
-
- The IRIX 6.5 desktop_eoe subsystems are incompatible with
- all previous IRIX releases (including WorkSpace).
-
-
- 2.6 _C_o_n_f_i_g_u_r_a_t_i_o_n__F_i_l_e_s
-
- Two new configuration directories were added in IRIX 6.3.
- They are ._d_e_s_k_t_o_p_h_o_s_t and ._d_e_s_k_t_o_p-<_h_o_s_t_n_a_m_e>/_0._0. These
- directories contain information specific to different hosts.
-
- Users who prefer to set up their machine so that the desktop
- does not start automatically can create a file called
- ._d_i_s_a_b_l_e_D_e_s_k_t_o_p in their home directory. This will cause
- the toolchest to display different contents. The desktop
- can also be disabled for all users of the machine by issuing
- the command ////eeeettttcccc////cccchhhhkkkkccccoooonnnnffffiiiigggg ddddeeeesssskkkkttttoooopppp ooooffffffff while logged in as
- root.
-
-
-
-
-
-
-
-
-
-
-
-
- - 5 -
-
-
-
- Various desktop tools create configuration files in a
- ._d_e_s_k_t_o_p-<_h_o_s_t_n_a_m_e> directory within the user's home
- directory. Except as discussed below, these files should
- not be edited by the user.
-
- The automatic startup of the file manager can be disabled by
- creating the file ._d_e_s_k_t_o_p-<_h_o_s_t_n_a_m_e>/_n_o_d_e_s_k_t_o_p. Should
- this file be present, the file manager will not start up,
- and icons will not be available on the background. Opening
- the Home Directory from the Desktop toolchest or running the
- _d_i_r_v_i_e_w command will still open up a directory view, but
- icons cannot be dragged to the background. This mode may be
- useful to users who do not wish to run the file manager, or
- who wish to have arbitrary images on their background. It
- may also be useful for machines with limited memory. To
- resume starting the file manager and having icons on the
- background, remove the file ._d_e_s_k_t_o_p-<_h_o_s_t_n_a_m_e>/_n_o_d_e_s_k_t_o_p,
- log out, and log in.
-
- The use of ._d_e_s_k_t_o_p-<_h_o_s_t_n_a_m_e>/_n_o_d_e_s_k_t_o_p differs from the
- use of ._d_i_s_a_b_l_e_D_e_s_k_t_o_p in that the former only disables the
- starting of the file manager. All other desktop features
- are still available.
-
- The ._d_e_s_k_t_o_p-<_h_o_s_t_n_a_m_e> directory also contains a log of all
- file transactions made through the desktop. Although
- slightly cryptic in format, this log may assist you in
- determining where a file has gone if you accidentally move a
- file to someplace unintentional. The log file is called
- ._d_e_s_k_t_o_p-<_h_o_s_t_n_a_m_e>/_l_o_g. After it grows to about 50K bytes,
- it is moved to ._d_e_s_k_t_o_p-<_h_o_s_t_n_a_m_e>/_l_o_g._b_a_k. The log size
- may be changed by setting the resource
- ****ddddeeeesssskkkkttttooooppppLLLLooooggggSSSSiiiizzzzeeee:::: <size>
- in the ._X_d_e_f_a_u_l_t_s or ._X_r_e_s_o_u_r_c_e_s files, where <size> is the
- maximum size in bytes of the log (including the backup
- copy). Setting <size> to 0 disables the log.
-
- Users familiar with X configuration should be aware that X
- resources modified by the IRIX Interactive Desktop
- Customization Panels will not modify the user's ._X_d_e_f_a_u_l_t_s
- or ._X_r_e_s_o_u_r_c_e_s files. Instead the resource settings will be
- saved in one of two places. If the resources affect a
- single application, they will be saved in $_H_O_M_E/._d_e_s_k_t_o_p-
- <_h_o_s_t_n_a_m_e>/<_a_p_p_n_a_m_e>, where <_a_p_p_n_a_m_e> is the application's
- class name. If the resource affects multiple applications
- it will be saved in $_H_O_M_E/._S_g_i_r_e_s_o_u_r_c_e_s. Panel changes that
- affect startup commands will be saved in $_H_O_M_E/._d_e_s_k_t_o_p-
- <_h_o_s_t_n_a_m_e>/_p_a_n_e_l_s_e_s_s_i_o_n or $_H_O_M_E/._d_e_s_k_t_o_p-
- <_h_o_s_t_n_a_m_e>/_d_e_s_k_t_o_p_e_n_v, the former being used for commands,
- and the latter being used for environment variables.
-
-
-
-
-
-
-
-
-
-
-
-
- - 6 -
-
-
-
- In 6.5, customization panels also write settings that should
- take effect immediately into the file $_H_O_M_E/._d_e_s_k_t_o_p-
- <_h_o_s_t_n_a_m_e>/_F_m_S_t_a_t_e and the file manager detects when that
- file changes and updates its state accordingly. The FmState
- file is not intended to be edited directly by the user.
-
- Users who used to launch applications from their ._s_g_i_s_e_s_s_i_o_n
- file will note that most of them are now launched through
- session management. One major difference from 4Sight is
- that session management is handled from 4Dwm, which is
- launched before the ._s_g_i_s_e_s_s_i_o_n is read. If there are
- environment variables that were set in ._s_g_i_s_e_s_s_i_o_n, these
- will not affect applications launched from session
- management. If you must set environment variables that
- affect applications, you can set them in $_H_O_M_E/._d_e_s_k_t_o_p-
- <_h_o_s_t_n_a_m_e>/_d_e_s_k_t_o_p_e_n_v. This file is in the /_b_i_n/_s_h syntax
- of the form
-
- VVVVAAAARRRRIIIIAAAABBBBLLLLEEEE====""""ssssttttrrrriiiinnnngggg"""";;;; eeeexxxxppppoooorrrrtttt VVVVAAAARRRRIIIIAAAABBBBLLLLEEEE
-
- Lines also containing the string
-
- #### VVVVAAAARRRRIIIIAAAABBBBLLLLEEEE ####
-
- have been modified by various panels; the string between the
- # symbols is a key for future panel modifications.
-
- Because session management will automatically restart
- applications that were launched, a ._s_g_i_s_e_s_s_i_o_n file can
- cause multiple copies of applications to run (one from
- ._s_g_i_s_e_s_s_i_o_n and one from 4Dwm). The desktop will no longer
- warn the user if such a file is detected; it will instead
- silently execute the contents of the file.
-
- When the IRIX Interactive Desktop is installed, the file
- /_u_s_r/_l_i_b/_X_1_1/_x_d_m/_X_s_e_s_s_i_o_n is not used as in a normal X
- environment. Instead, the file /_u_s_r/_l_i_b/_X_1_1/_x_d_m/_X_s_e_s_s_i_o_n._d_t
- is invoked. If the desktop is disabled through the use of
- _c_h_k_c_o_n_f_i_g or the ._d_i_s_a_b_l_e_D_e_s_k_t_o_p file mentioned above,
- _X_s_e_s_s_i_o_n is used instead of _X_s_e_s_s_i_o_n._d_t.
-
- If the user has a ._x_s_e_s_s_i_o_n file, it will override the
- system _X_s_e_s_s_i_o_n._d_t file, and may prevent some of the IRIX
- Interactive Desktop features from being started. In 6.5,
- the desktop will no longer warn the user if such a file is
- detected; it will instead silently execute the contents of
- the file.
-
- The toolchest is configured using the file /_u_s_r/_l_i_b/_X_1_1/
- _s_y_s_t_e_m._c_h_e_s_t_r_c. This file has changed since the IRIX 6.2
- release. Users who wish to edit their toolchest contents
-
-
-
-
-
-
-
-
-
-
-
- - 7 -
-
-
-
- may wish to copy the file /_u_s_r/_l_i_b/_X_1_1/_n_o_d_e_s_k_t_o_p._c_h_e_s_t_r_c
- onto either their private $_H_O_M_E/._c_h_e_s_t_r_c to affect only
- their account, or on top of /_u_s_r/_l_i_b/_X_1_1/_s_y_s_t_e_m._c_h_e_s_t_r_c to
- affect all accounts on the machine. The
- /_u_s_r/_l_i_b/_X_1_1/_n_o_d_e_s_k_t_o_p._c_h_e_s_t_r_c file is also the toolchest
- configuration file that will be used if the user executes
- ////eeeettttcccc////cccchhhhkkkkccccoooonnnnffffiiiigggg ddddeeeesssskkkkttttoooopppp ooooffffffff or creates a ._d_i_s_a_b_l_e_D_e_s_k_t_o_p
- file. In the 6.3, 6.4, and 6.5 releases, the layout of a
- remote toolchest is controlled by the
- /_u_s_r/_l_i_b/_X_1_1/_r_e_m_o_t_e._c_h_e_s_t_r_c file.
-
- Users who already have a $_H_O_M_E/._c_h_e_s_t_r_c will not see the new
- IRIX 6.5 toolchest, since $_H_O_M_E/._c_h_e_s_t_r_c takes precedence
- over /_u_s_r/_l_i_b/_X_1_1/_s_y_s_t_e_m._c_h_e_s_t_r_c. To allow users to see the
- new toolchest, the first time they log in their ._c_h_e_s_t_r_c
- file will be renamed to ._c_h_e_s_t_r_c._b_a_k and a warning given.
- They may rename it back if they wish, possibly editing it to
- include the new toolchest contents. Alternatively, they may
- use the toolchest "include" facility to include a personal
- ._a_u_x_c_h_e_s_t_r_c. The latter has the advantage that future
- changes to the _s_y_s_t_e_m._c_h_e_s_t_r_c will be automatically picked
- up.
-
- The Background customization panel gets its list of
- backgrounds from the file /_u_s_r/_l_i_b/_X_1_1/_s_y_s_t_e_m._b_a_c_k_g_r_o_u_n_d_s.
- It accepts files in either the X bitmap format or the X
- pixmap (xpm) format, and can also accept commands to
- execute, such as _t_w_i_l_i_g_h_t.
-
-
- 2.7 _F_i_l_e_s__N_o_t__L_i_s_t_e_d__b_y__vvvv_eeee_rrrr_ssss_iiii_oooo_nnnn_ssss
-
- The ._d_e_s_k_t_o_p-<_h_o_s_t_n_a_m_e> directory and its contents as well
- as the ._d_e_s_k_t_o_p_h_o_s_t and its contents are not listed by the
- _v_e_r_s_i_o_n_s command.
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-